This repository was archived by the owner on Jun 7, 2026. It is now read-only.
chore(gateway): remove legacy userEmail/INBOX_ZERO fields - #76
Merged
Conversation
Remove unused `userEmail` field from all API request schemas and `INBOX_ZERO_*` environment variable handling. This was leftover from a prototype email inbox assistant that is no longer active. Neither the TypeScript nor Python SDK exposed `userEmail` in their public API, so this is a non-breaking change. Closes #71
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
userEmailfield from all API request schemasINBOX_ZERO_*environment variable handling frombuildClaudeEnvThis was leftover code from a prototype email inbox assistant that is no longer active.
Notes
Neither the TypeScript nor Python SDK exposed
userEmailin their public API, so this is a non-breaking change. Thechore:commit type ensures release-please will not treat this as a breaking change.Closes #71